SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
Go

Go static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your GO code

  • All rules 70
  • Vulnerability20
  • Bug7
  • Security Hotspot14
  • Code Smell29
 
Tags
    Impact
      Clean code attribute
        1. Hard-coded secrets are security-sensitive

           Security Hotspot
        2. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        3. Using publicly writable directories is security-sensitive

           Security Hotspot
        4. Using clear-text protocols is security-sensitive

           Security Hotspot
        5. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        6. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        7. Searching OS commands in PATH is security-sensitive

           Security Hotspot
        8. Creating cookies without the "HttpOnly" flag is security-sensitive

           Security Hotspot
        9. Setting loose POSIX file permissions is security-sensitive

           Security Hotspot
        10. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        11. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot
        12. Formatting SQL queries is security-sensitive

           Security Hotspot
        13. Hard-coded credentials are security-sensitive

           Security Hotspot
        14. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Constructing arguments of system commands from user input is security-sensitive

        intentionality - logical
        security
        Security Hotspot
        • cwe
        • injection

        Constructing arguments of system commands from user input is security-sensitive. It has led in the past to the following vulnerabilities:

        • CVE-2016-9920
        • CVE-2021-29472

        Arguments of system commands are processed by the executed program. The arguments are usually used to configure and influence the behavior of the programs. Control over a single argument might be enough for an attacker to trigger dangerous features like executing arbitrary commands or writing files into specific directories.

        Ask Yourself Whether

        • Malicious arguments can result in undesired behavior in the executed command.
        • Passing user input to a system command is not necessary.

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        • Avoid constructing system commands from user input when possible.
        • Ensure that no risky arguments can be injected for the given program, e.g., type-cast the argument to an integer.
        • Use a more secure interface to communicate with other programs, e.g., the standard input stream (stdin).

        Sensitive Code Example

        Arguments like -delete or -exec for the find command can alter the expected behavior and result in vulnerabilities:

        import (
        	"fmt"
        	"net/http"
        	"os/exec"
        )
        
        func ListDirectory(w http.ResponseWriter, req *http.Request) {
        	dirs := req.URL.Query()["dir"]
        
        	output, _ := exec.Command("/usr/bin/find", dirs...).CombinedOutput() // Sensitive
        	fmt.Fprintf(w, "Output: %s", output)
        }
        

        Compliant Solution

        Use an allow-list to restrict the arguments to trusted values:

        import (
        	"fmt"
        	"net/http"
        	"os/exec"
        )
        
        var allowed = map[string]bool{"/tmp": true}
        
        func ListDirectory(w http.ResponseWriter, req *http.Request) {
        	dirs := req.URL.Query()["dir"]
        
        	for _, dir := range dirs {
        		if _, ok := allowed[dir]; !ok { // Validator
        			fmt.Fprintf(w, "Error")
        			return
        		}
        	}
        
        	output, _ := exec.Command("/usr/bin/find", dirs...).CombinedOutput()
        	fmt.Fprintf(w, "Output: %s", output)
        }
        

        See

        • OWASP - Top 10 2021 Category A3 - Injection
        • OWASP - Top 10 2017 Category A1 - Injection
        • CWE - CWE-88 - Argument Injection or Modification
        • CVE-2021-29472 - PHP Supply Chain Attack on Composer
        • STIG Viewer - Application Security and Development: V-222609 - The application must not be subject to input handling vulnerabilities.
          Available In:
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use